<text><span class="style20">trl—N</span><span class="style2"> changes the height of the background text at the top of the standard layout. The height is increased one line at a time until the bottom of the layout is reached, then the height is set to zero. At the zero point, you may proceed with Ctrl—o, and obtain a layout which contains nothing but card text!</span><span class="style20">Ctrl—O</span><span class="style2"> changes the arrangement of the objects in the standard document in minor ways, showing or hiding certain objects, and changing their sizes. There are four basic tiling layouts. Ctrl—o cycles through these layouts.</span></text>
</content>
<content>
<layer>background</layer>
<id>38</id>
<text>You can change the size of the card or the window (change the window size with Shift—Command—E, change the card size with the Stack Info... dialog). Ctrl—o will replace objects in the corners, and re–tile the text.All automatic re–tiling commands work with all the model formats I have provided.</text>
</content>
<name>Automatic Object Rearrangement</name>
<script></script>
</card>
card_2422.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style2">ou may change the style or the font of any field. You may reposition, resize, or hide any object found in the model layouts, but you can’t delete an object, since the hypertext program will look for it every now and again. </span><span class="style20"></span><span class="style2">Do not change </span><span class="style22">functional</span><span class="style2"> properties of a standard button or field. If you do, you will experience anomalies.</span><span class="style22">Field functional properties</span><span class="style2">: Name, Shared Text, Don’t Search, and Auto Tab.</span><span class="style22">Button functional properties</span><span class="style2">: ID, Name, Auto Hilite, Shared Hilite, and Show Name.</span></text>
</content>
<content>
<layer>background</layer>
<id>38</id>
<text>A common change involves the field type. When composing hypertext, you will find the scroll bars useful. Many authors recommend that you get rid of the scroll bars when the hypertext is finished. If your text doesn’t fit in the window, place the remainder on the next card, since moving to the next card is easier for the reader than using scroll bars.I have also observed that Power Book users prefer large characters. If you want larger characters than the ones I use (they look fine on my old SE) I recommend that you change all your model formats, so you only have to do it once.</text>
</content>
<name>Changing Object Properties</name>
<script></script>
</card>
card_2921.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>You may add your own buttons and fields, and I obviously won’t have a lot to say about how, why, what, or how many. Remember that Ctrl—N and Ctrl—o will only rearrange standard background objects. If you have added buttons or fields to the layout, they will be ignored and you will have to reposition them yourself after issuing these commands or after changing the card size. As a compromise, I have left a margin at the bottom for buttons in 2 of the Ctrl—o layouts.</text>
</content>
<content>
<layer>background</layer>
<id>38</id>
<text><span class="style2">hen using additional fields, be sure to name the fields and add the appropriate names to the field lists in “</span><span class="style11"><a href="#" class="group">Dock Export</a></span><span class="style2">” and “</span><span class="style11"><a href="#" class="group">Dock Import</a></span><span class="style2">” if you use these utilities.Also remember to edit the Print Report Templates (or add new ones) to include all the text if you use the report facility with additional fields.</span></text>
</content>
<name>Adding Buttons and Fields</name>
<script></script>
</card>
card_5971.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The “Print Stack...” and “Print Report...” facilities may be modified for your specific site. As far as I know, the facilities in all standard documents work with both “US Letter” and “A4” paper.</text>
</content>
<content>
<layer>background</layer>
<id>38</id>
<text>I recommend that you check the “Page Setup...” and “Print Stack...” dialogs before cloning the models. It is easier to reconfigure one model than to reconfigure many offspring.</text>
</content>
<name>Changing Printing Facilities</name>
<script></script>
</card>
card_4691.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style2">his is a somewhat advanced topic, but it’s really not that difficult.In order to obtain a new model stack, simply clone an existing stack and edit the clone’s background.Remark: Store each different model in a different stack. This is required by the </span><span class="style11"><a href="#" class="group">Dock Import</a></span><span class="style2"> Utility.</span></text>
</content>
<content>
<layer>background</layer>
<id>38</id>
<text>I have used a small portion of each background script for my address and for launching the hypertext program. Feel free to work around my script—there’s plenty of room left—but please don’t erase it, or the hypertext won’t work anymore! </text>
</content>
<name>Creating New Models</name>
<script></script>
</card>
card_6359.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>All Dock standard document layouts (backgrounds) can be mixed in any combination in hypertext compositions, but this will rarely be needed, since a different layout can just as easily be reached in a different stack using hypertext.Here, I have used the Model Layout with 2 columns, and I have hidden the second column to make room for the picture.Note: The “hcp” message must be used here to hide the picture before editing links or catalogs.</text>
